Dynomotion

Group: DynoMotion Message: 3002 From: fireup_kev Date: 1/8/2012
Subject: Interpreter Slows down over time /w KMotion_dotNet
I've noticed the Interpreter execution time slows down over repeated runs of large GCode files. Even in simulation mode a GCode of about 15,000 lines (ear.ngc) will first take about 1 seconds to run. Then repeated run of the same GCode will increase by 0.05 to 0.1 seconds each time. Has anyone else experienced this? The only work-around I have at the moment is to kill the instance and re-initialize the class.

Kevin
Group: DynoMotion Message: 3003 From: Tom Kerekes Date: 1/8/2012
Subject: Re: Interpreter Slows down over time /w KMotion_dotNet
Hi Kevin,
 
Strange. What Application are you using to make the Call?  Specificlly which class are you deleting and re-newing?  Are you registering call backs?
 
Thanks
TK

Group: DynoMotion Message: 3004 From: fireup_kev Date: 1/8/2012
Subject: Re: Interpreter Slows down over time /w KMotion_dotNet
I have C# program that is communicating to the board via KMotion_dotNet.dll. I'm calling _Controller.Interpreter.Interpret(filename) to start the gCode. I'm registering the InterpreterCompleted callback to stop my timer. After each run, it will take longer to complete the same task.

If I issue the follow and re-initialize my variables, the run will be fast again.

_Controller.Disconnect();
_Controller = null;
_Controller = new KMotion_dotNet.KM_Controller();


Kevin

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Kevin,
>  
> Strange. What Application are you using to make the Call?  Specificlly which class are you deleting and re-newing?  Are you registering call backs?
>  
> Thanks
> TK
>
> From: fireup_kev <kliboon@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, January 8, 2012 12:07 PM
> Subject: [DynoMotion] Interpreter Slows down over time /w KMotion_dotNet
>
>
>  
> I've noticed the Interpreter execution time slows down over repeated runs of large GCode files. Even in simulation mode a GCode of about 15,000 lines (ear.ngc) will first take about 1 seconds to run. Then repeated run of the same GCode will increase by 0.05 to 0.1 seconds each time. Has anyone else experienced this? The only work-around I have at the moment is to kill the instance and re-initialize the class.
>
> Kevin
>
Group: DynoMotion Message: 3005 From: fireup_kev Date: 1/8/2012
Subject: Re: Interpreter Slows down over time /w KMotion_dotNet
Never mind, I found my problem. I was re-registering the same callback every time I hit the run button. I only need to do it once.. duh :)

--- In DynoMotion@yahoogroups.com, "fireup_kev" <kliboon@...> wrote:
>
> I have C# program that is communicating to the board via KMotion_dotNet.dll. I'm calling _Controller.Interpreter.Interpret(filename) to start the gCode. I'm registering the InterpreterCompleted callback to stop my timer. After each run, it will take longer to complete the same task.
>
> If I issue the follow and re-initialize my variables, the run will be fast again.
>
> _Controller.Disconnect();
> _Controller = null;
> _Controller = new KMotion_dotNet.KM_Controller();
>
>
> Kevin
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Kevin,
> >  
> > Strange. What Application are you using to make the Call?  Specificlly which class are you deleting and re-newing?  Are you registering call backs?
> >  
> > Thanks
> > TK
> >
> > From: fireup_kev <kliboon@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Sunday, January 8, 2012 12:07 PM
> > Subject: [DynoMotion] Interpreter Slows down over time /w KMotion_dotNet
> >
> >
> >  
> > I've noticed the Interpreter execution time slows down over repeated runs of large GCode files. Even in simulation mode a GCode of about 15,000 lines (ear.ngc) will first take about 1 seconds to run. Then repeated run of the same GCode will increase by 0.05 to 0.1 seconds each time. Has anyone else experienced this? The only work-around I have at the moment is to kill the instance and re-initialize the class.
> >
> > Kevin
> >
>